|
|
|
| |
        
|
 |
|
To access the contents, click the chapter and section titles.
Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
12.6.2. User and Group Migration Options: UsernamesOptions specified under the Usernames tab in the User and Group Options dialog box instruct NWCONV on how to handle duplications in migrated usernames (see Figure 12.19). The four options are
12.6.3. User and Group Migration Options: Group NamesOptions specified under the Group Names tab instruct NWCONV on how to handle duplications in group names (see Figure 12.20). The three options have the same functions that are applied to usernames except that groups on the NT server cannot be overwritten by migrated NetWare groups.
12.6.4. User and Group Migration Options: DefaultsTwo options concerning supervisor rights are handled under the Defaults tab (see Figure 12.21):
12.6.5. Selecting User and Group Options: Mapping FileAn alternative approach to migrating user and group objects is available to you through a mapping file. You use a mapping file to assert extra control over destination user and group names and passwords. You may either create a mapping file or edit an existing one by selecting the appropriate button on the User and Group Options dialog box. Figure 12.22 shows the Create Mapping File dialog box.
NWCONV creates the mapping file for you when you choose the Create button from the User and Group Options dialog box. The utility creates the mapping file based on your responses to similar options for passwords and groups. The mapping file, which is simply a comma-delineated text file, contains two headers denoted by brackets ([Users] and [Groups]), where NetWare usernames and group names are specified. The NT username is listed in the field beside the NetWare username, and then the destination password is listed (see Figure 12.23). You can save and edit the file at any time.
The usefulness of the mapping file is evident when NetWare usernames or groups already exist in the target NT domain. You could manually exclude those users or groups from the migration by commenting out their entries in the mapping file or rename accounts individually to meet your Windows NT naming convention. You can also use the mapping file to define individual passwords. After you select a mapping file in the User and Group Options dialog box, the options previously discussed under the Passwords, Usernames, and Group Names tabs are grayed out (see Figure 12.24). The mapping file is then used exclusively for user and group migration.
12.7. Selecting File OptionsThe File Options dialog box allows the administrator to identify directories and files on NetWare volumes for migration to an NTFS partition (see Figure 12.25). The columns on the left list all mounted volumes on the specified NetWare server, including CD-ROM volumes.
From the File Options dialog box, you have the option to delete volumes from migration, modify their destination path and share name on the NT server, and identify only specific files and directories for migration. The Add button becomes active only after you delete a volume from the list. 12.7.1. File Migration Options: Modifying Destination Directory Paths and Share NamesYou might want to modify the destination paths for your files on the NT server. By default, NetWare volume names are retained as both directory and share names on the NTFS partition (see Figure 12.26).
To change the destination path or share name, click the New Share button on the Add Volume to Copy dialog box. A second dialog box is displayed as shown in Figure 12.26. Here, you can provide an alternative share name and the desired path on an NTFS partition. The example I provided points to my NTFS-formatted partition on the MAILGATE server. Click OK to continue. When you return to the File Options dialog box, changes are reflected in the columns on the left as seen in Figure 12.25. 12.7.2. File Migration Options: Selecting Files and Directories for MigrationYou might want to deselect some files and directories that are migrated to NT. Migrating nearly all of the SYS: volume, for example, is impractical; you can usually ignore the contents of ETC, PUBLIC, SYSTEM, and LOGIN. However, you might want to migrate user home directories. NWCONV allows for migration down to the individual file level. In the example in Figure 12.27, the NetWare volume is identified as DMEVI: and the directories that aren’t to be transferred (because all the directories and files are selected by default) are deselected. Simply select the file or directory objects you want to transfer and click OK to continue.
|
|
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited.
|
)
)
)
)
)
)
)
)
)
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}